The Original Shareware 1.1

home *** CD-ROM | disk | FTP | other *** search

/ The Original Shareware 1.1 / The Original Shareware (WeMake CDs)(Volume 1.1)(CDs, Inc)(1993).iso / 36 / 386pcbdv.zip / 386PCBDV.TXT

Wrap

Text File | 1988-05-18 | 19KB | 376 lines

386PCBDV.TXT By Joseph Sheppard The Ledge PCBoard (818) 352-3620 This file describes the method I have used to run three nodes (two live and one with no modem for the Sysop) using PCBoard 12.1, Desqview 2.01 and Quarterdeck's Expanded Memory Manager 386 on a 16 MHz AMI 386 AT. I am writing this file because several months ago, when I first tried to setup my system, very few systems were running multi-nodes under Desqview on an 80386 based machine using the virtual 86 mode. It took quite a bit of help from two local Sysops, Tom Tcimpidis of The MOG-UR'S EMS (818) 366-1238 and Ken Ough of LUNACY PCBoard (818) 894-1248. Without the help I received from Tom and Ken, I'm not sure I would have been able to figure it out. It is assumed that the reader is running a machine with an 80386 microprocessor running at least 16 MHz, and that you are very familiar with PCBoard 12.1, Desqview 2.01 and QEMM 4.0. My specific system includes 4096 K of RAM. All the memory above 640K is eXtended memory. QEMM 4.0 will convert standard eXtended memory on a 386 machine into exPanded memory that can be used for running programs. If you are running more or less memory, you can adjust the figures mentioned here to match your system. You will probably need at least 2 megabytes of extended RAM in order to run 2 live PCBoard nodes and have enough room left for a good sized third window. One of the problems I encountered is that the Desqview manual assumes that there is a single user on the system that is present at the terminal while multi-tasking is taking place. Many of the default settings assume that the user wants the most speed and processing power put toward the program in the foreground. A multi-node BBS, however, can have two remote users with a third at the local keyboard. Nobody wants to be on the short end of the stick! Using the settings described here I have been able to run both nodes of the BBS and a third window for my use as either a no-modem node, or just space to play around in at very respectable speeds. I happen to run a USRobotics Courier HST modem on node 1 with the port open at 19200 baud. My log constantly reflects cps ratings ranging from 1000-1200 cps for the high speed callers, while another caller is present on node 2, and I am busy in a third window. CONFIG.SYS ----------- The first thing to alter is your CONFIG.SYS. Mine looks like this: DEVICE=QEMM.SYS FCBS=48,48 FILES=48 DEVICE=QEMM.SYS --------------- Converts all of your eXtended memory to exPanded so that it can be used to run programs in the virtual 86 mode. FCBS=48,48 ---------- This is the setting suggested to run PCBoard with a multi-tasker. It is suggested that you have 16 FCBS per node. FILES=48 -------- This is the Files statement suggested to run PCBoard with a multi-tasker. It is suggested that you have 16 file handles per node. A smaller setting will save RAM, but may result in "path configuration errors" Regarding BUFFERS, I am running a two megabyte disk cache using Speedcache, which is distributed with Speedstor hard drive partitioning software, so I do not use a BUFFERS= statement. Before using the cache, I used to use BUFFERS=50. DESQVIEW SETUP -------------- Go into your Desqview directory and type SETUP. Go to the performance menu. Mine looks like this: ╔1══Advanced═Setup:═Performance══════════╗ ║ ║ ║ Task Processing Time (in Clock Ticks) ║ ║ Foreground: 1 ║ ║ Background: 1 ║ ║ ║ ║ Memory Usage (in K) ║ ║ Common Memory: 12 ║ ║ DOS Buffer for EMS: 30 ║ ║ ║ ║ Optimize communications? (Y/N): Y ║ ║ Allow swapping of programs? (Y/N): Y ║ ║ Manage printer contention? (Y/N): Y ║ ║ ║ ║ Next field Tab ║ ║ Backup menu Esc ║ ║ DONE ─┘ ║ ║ ║ ╚════════════════════════════════════════╝ TASK PROCESSING TIME (in Clock Ticks) ------------------------------------- The default settings here were Foreground: 9, Background: 3. From remote the system looked like PCBoard re-written for the Commodore Vic-20! Really slow and jerky with callers on both nodes. For awhile I ran it with 3 and 3, then 2 and 2, but these settings, while providing VERY smooth scrolling at all modem speeds still caused erratic remote keyboard entry. Kind of like PC Pursuit, where you type and the text on the screen is about 3 letters behind you. The Desqview manual says not to set it below 2 and 2, but with my system 1 and 1 provided smooth scrolling and excellent remote keyboard entry. Memory Usage (in K) -------------------- Common Memory: 12 is the default. Didn't seem to improve anything when I changed it to higher, so I just kept it there. DOS Buffer for EMS: 30. The default is 2K. The maximum that the manual states is effective is 30. Because I was looking for performance rather than efficient use of memory, I chose the maximum. If your available memory dwindles too low, this would be place you could cut back without a big loss of performance. Optimize Communications? ------------------------ This is the default. No change. Allow swapping of programs? --------------------------- Yes is the default. Nothing exploded, so I didn't change it. However, as the manual states, DO NOT allow a modem program to be swapped out of memory! Manage Printer Contention? -------------------------- The default is NO. This one had to be changed to fix what seemed to be a totally unrelated problem. While running Desqview, I couldn't seem to use the CTTY command to go to DOS from remote. From the local side, I could type CTTY COM1 from the DOS prompt, and instead of disappearing to COM1, it would just bounce the DOS prompt back at me again like nothing had happened. Finally I called Quarterdeck and they told me to change this setting to YES. This fixed the problem, while (at this point anyway) not causing any new ones. PROGRAM INFORMATION ------------------- All three of my PCBoard nodes are set-up exactly the same as far as memory allocated, and general options. The first set-up screen for node 1 looks like this: ╔1══Change═a═Program═══════════════════════════════════════════════════════════╗ ║ Change a Program ║ ║ ║ ║ Program Name............: PCBoard Node 1 ║ ║ ║ ║ Keys to Use on Open Menu: N1 Memory Size (in K): 300 ║ ║──────────────────────────────────────────────────────────────────────────────║ ║ Program...: d:\pcb\board ║ ║ ║ ║ Parameters: ║ ║ ║ ║ Directory.: d:\pcb ║ ║──────────────────────────────────────────────────────────────────────────────║ ║ Options: ║ ║ Writes directly to screen......: [Y] ║ ║ Displays graphics information..: [N] ║ ║ Can be swapped out of memory...: [N] ║ ║ Requires floppy diskette.......: [N] ║ ║ ║ ║ Press F1 for advanced options Press ─┘ when you are DONE ║ ╚══════════════════════════════════════════════════════════════════════════════╝ Memory Size in K: ----------------- Can be less, but I made it 300K just to be sure. All functions seem to work fine with this allocation. Jump To DOS, Doors and External Protocols all function fine. Even under this high overhead for performance set-up you should still be able to allocate over 400K to a window if need be. Program....d:\pcb\board ----------------------- This executes the BOARD.BAT file. The only change I have made in BOARD.BAT is that I have it execute DVANSI before running PCBOARD. This will eliminate the ANSI codes you may have seen when you try to run PCBoard inside of Desqview. Can be swapped out of memory ---------------------------- As with ANY communications program under Desqview, this should always be set to NO. Writes Directly to Screen ------------------------- I originally had this set to NO, but Doors compiled with a particular version of DOORPCH wrote directly to the screen. You may want to set this to NO, and if you find that you have screen problems inside of certain doors, set it to YES. PCBoard itself dosen't write to screen at all, so if you don't use doors, set it to NO. ADVANCED OPTIONS ---------------- Hit F1 to go to the Advanced Options menu..some things will require changing. Here is my Advanced option screen for Node 1: ╔1══Change═a═Program═══════════════════════════════════════════════════════════╗ ║ Change a Program Advanced Options ║ ║ ║ ║ System Memory (in K).......: 0 Maximum Program Memory Size (in K)..: ║ ║ ║ ║ Script Buffer Size.......: 1000 Maximum Expanded Memory Size (in K): ║ ║ ║ ║ Text Pages: 1 Graphics Pages: 0 Initial Mode: Interrupts: 00 to FF ║ ║──────────────────────────────────────────────────────────────────────────────║ ║ Window Position: ║ ║ Maximum Height: 25 Starting Height: 25 Starting Row...: 0 ║ ║ Maximum Width.: 80 Starting Width.: 80 Starting Column: 0 ║ ║──────────────────────────────────────────────────────────────────────────────║ ║ Shared Program ║ ║ Pathname..: ║ ║ ║ ║ Data......: ║ ║──────────────────────────────────────────────────────────────────────────────║ ║ Options: ║ ║ Close on exit to DOS.........: [N] Uses its own colors.........: [Y] ║ ║ Allow Close Window command...: [Y] Runs only in foreground.....: [N] ║ ║ Uses math coprocessor........: [N] Keyboard conflict (0-4).....: [0] ║ ║ ║ ║ Press F1 for standard options Press ─┘ when you are DONE ║ ╚══════════════════════════════════════════════════════════════════════════════╝ Starting Height: 25 Starting Width.: 80 ------------------- This will keep Desqview from sticking you in a half sized window. To switch between nodes just tap ALT twice real fast. Uses it's own colors : Y ------------------------ Set this to YES if you want PCBoards normal colors instead of Desqview's reverse screen stuff. Runs only in foreground: N -------------------------- Set this to NO to insure that Desqview won't stop one of your nodes because it's in background. Questions I get asked all the time: ---------------------------------- Q: Why do I get ANSI codes when I try to enter the board? A: You need to run DVANSI.COM in each and every window. Just stick the word DVANSI at the top of BOARD.BAT and your problem will go away. Q: I have a USRobotics HST modem. Downloads go very fast (1100 cps and better!) but uploads from callers at 19200 bps using Ymodem-G and Imodem always abort! What can I do about it? A: This was a hopeless case until recently. I replaced my 16450 serial chip with a 16550A. PCBoard 12.1 does not support the 16550A, but DSZ does. This means that your users will have to use Zmodem (1000 cps on my board) or Ymodem-G Batch (1100+ cps) to upload files until Qmodem and PCBoard's internal protocols support the 16550A. I don't know if this replacement will work for everyone, but it certainly did the trick for me. Q: How do I make Desqview automatically open my PCBoard windows? I want my board to come back up automatically in case of a power failure. Now it just runs desqiew and sits at the opening screen! A: You have to define a "Start-up Script". Refer to your Desqview manual for the specifics. In General, you have to use the "Learn" feature, and name your script "!" (without the Quotes). Desqview will automatically start with that script that you have created using the "Learn" function. Q: I get a message saying somethign about a "Non-swappable window", then everything stops! What am I doing wrong? A: You probably have your window size too large. Open the Memory Status window and see what your largest available Expanded Memory is. Reduce your window size to about 20K less than that figure and try again. Q: The largest window I can open is only about 200K. How come you can open 300K windows? A: Some people can open 500K windows! The trick is to rename XDV.COM to to DV.COM. This makes Desqveiw load itself into little nooks and crannies that you aren't using so you can have the maximum amount of RAM per window. If your windows are still smaller than you'd like, take a look at your CONFIG.SYS and AUTOEXEC.BAT. Are you still using ANSI.SYS? You don't need it anymore because you are using DVANSI...that can free up a few bytes. Look for things that you can do without, and your window size will get larger. Q: When should I run my cache program, before or after Desqview starts? A: ALWAYS run cache programs BEFORE Desqveiw or any multi-tasker. If you try to run your cache inside a window, you will probably have a very big problem with your hard disk. Q: Why are you using QEMM 4.0 instead of 4.1? A: Because I found that QEMM 4.1 won't allow me execute a warm boot from remote by using any of the various BOOT.COM type utilities. I like to be able to do this just in case one or the other node crashes while I'm at work. Then I can just drop to DOS on the working node and re-boot the machine. Autoexec.bat executes Desqview, Desqveiw executes the startup scripts for the two PCBoard Nodes...and I'm in business. Q: Can I run two nodes using Desqview on a 286? A: Yes. You won't have many of the 386 options, but it is possible. To run two nodes on a 286, you'll need to install QEXT.SYS and make sure that you have renamed XDV.COM to DV.COM. Then you'll need to experement to find the maximum amount of RAM your configuration will allow two PCBoard nodes to have without crashing or attempting to swap. Q: Where can I find other Desqview users to exchange tips and tricks with? A: One excellent place for general Desqview info is the Desqveiw Conference at The Sound of Music BBS. This conference is visited reguarly by Gary Saxer of Quarterdeck who has been very helpful to many users. The Sound of Music can be reached at (516) 536-8723 or (516) 536-6819. These are the specific things that I had to change to get it to run on my system. Yours may be different. I am reachable on my BBS which is listed at the top of page one if you need assistance. Unfortunately, I am one of those paranoid sysops that require mail-in registration. However, I wave all that for visiting Sysops. So, if you call, just leave me a [C]omment with your questions, and next time you call, I'll have you validated and will hopefully have some sort of suggestions for whatever problems you might be having. Good Luck! -Joseph Sheppard